The DNS implementation must provide audit record generation capability for organization defined auditable events occurring within DNS.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-34054	SRG-NET-000113-DNS-000063	SV-44507r1_rule		Medium

Description
Auditing and logging are key components of any security architecture. It is essential for security personnel to know what is being performed on the system, where an event occurred, when an event occurred, and by whom the event was triggered, in order to compile an accurate risk assessment. Logging the actions of specific events provides a means to investigate an attack, recognize resource utilization or capacity thresholds, or to simply identify an improperly configured DNS system. If auditing is not comprehensive, it will not be useful for intrusion monitoring, security investigations, and forensic analysis.

Description

Auditing and logging are key components of any security architecture. It is essential for security personnel to know what is being performed on the system, where an event occurred, when an event occurred, and by whom the event was triggered, in order to compile an accurate risk assessment. Logging the actions of specific events provides a means to investigate an attack, recognize resource utilization or capacity thresholds, or to simply identify an improperly configured DNS system. If auditing is not comprehensive, it will not be useful for intrusion monitoring, security investigations, and forensic analysis.

STIG	Date
Domain Name System (DNS) Security Requirements Guide	2012-10-24

Details

Check Text ( C-42020r1_chk )
Review the DNS implementation to determine if organization defined auditable events are being audited by the system. If organizationally defined auditable events are not being audited, this is a finding.

Fix Text (F-37968r1_fix)
Configure the DNS system capability to audit organization defined auditable events.